Dynomotion

Group: DynoMotion Message: 11728 From: moray_cuthill Date: 6/19/2015
Subject: Win7 64bit driver problem

I'm just getting around to doing some testing on my recently updated laptop (went from XP to Win7 64bit install on a new hard disk), but I had issues getting the drivers to install and for KMotion to detect the board using the latest 4.33L drivers. Directing the windows installer to an old 4.31s install, solved the problem.


The error message I kept receiving was -

Windows found driver software for your device but encountered an error while attempting to install it.


Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or might be malicious software from an unknown source. (Code 52)


I tried disabling my anti-virus, but it made no difference.

Has there been any change in the newer drivers?


Moray
Group: DynoMotion Message: 11729 From: Tom Kerekes Date: 6/19/2015
Subject: Re: Win7 64bit driver problem
Hi Moray,

That message indicates it won't load the drivers because they are not digitally signed (which they are not).

You must allow unsigned drivers.  That shouldn't be any different from before.  I've tested the drivers on W8.1 64bit and haven't heard of anyone else having issues.  See:


HTH
Regards
TK

Group: DynoMotion Message: 11731 From: Moray Cuthill Date: 6/20/2015
Subject: Re: Win7 64bit driver problem

Hi Tom,

I'd already seen that. When prompted I did select to allow unsigned drivers, but they still failed. I'm now wondering if it was Avast causing the problem, and the drivers in the 4.33L folder somehow got flagged up and Windows just wouldn't use them, even after I disabled the Avast shields.

It's all working fine now, but thought I should mention it in case anybody else gets problems.

Thanks,
Moray

On 19 Jun 2015 23:45, "Tom Kerekes tk@... [DynoMotion]" <DynoMotion@yahoogroups.com> wrote:
 

Hi Moray,

That message indicates it won't load the drivers because they are not digitally signed (which they are not).

You must allow unsigned drivers.  That shouldn't be any different from before.  I've tested the drivers on W8.1 64bit and haven't heard of anyone else having issues.  See:


HTH
Regards
TK